Data processing methods, apparatuses, devices, and media

ABSTRACT

Embodiments of the present specification disclose data processing methods, apparatuses, devices, and media. One method includes the following: receiving a data use request; determining data to be used based on the data use request; determining one or more approvers of the data to be used; sending an approval instruction to the one or more approvers, wherein the approval instruction instructs the one or more approvers to approve the data use request; receiving feedback data from the one or more approvers; and determining that the data use request is approved if the feedback data satisfies a predetermined condition.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No.202010723431.6, filed on Jul. 24, 2020, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

The present application relates to the field of computer technologies,and in particular, to data processing methods, apparatuses, devices, andmedia.

BACKGROUND

At present, the Internet generates and stores various data, includingdata related to user privacy and other privacy, and how to controllablyuse the Internet data is an important issue.

In view of this, there is a need for effective and efficient datamanagement and control solutions.

SUMMARY

Embodiments of the present specification provide data processingmethods, apparatuses, devices, and media, which are used to solve thetechnical problem of how to effectively and efficiently manage andcontrol Internet data.

In order to solve the previously described technical problem, theembodiments of the present specification adopt the following technicalsolutions:

The embodiments of the present specification provide a data processingmethod, including the following: a data use request is received, anddata to be used is determined based on the data use request; one or moreapprovers corresponding to the data to be used are determined; anapproval instruction is sent to each approver, where the approvalinstruction is used for instructing each approver to approve the datause request; and approval feedback data of each approver is received,and it is determined that the data use request is approved if theapproval feedback data satisfies a predetermined condition.

The embodiments of the present specification provide a data processingapparatus, including the following: a data determination module,configured to receive a data use request, and determine data to be usedbased on the data use request; an approval determination module,configured to determine one or more approvers corresponding to the datato be used; an approval initiation module, configured to send anapproval instruction to each approver, where the approval instruction isused for instructing each approver to approve the data use request; andan approval judgment module, configured to receive approval feedbackdata of each approver, and determine that the data use request isapproved if the approval feedback data satisfies a predeterminedcondition.

The embodiments of the present specification provide a data processingdevice, including the following: at least one processor; and a memorycommunicably coupled to the at least one processor, where the memorystores instructions executable by the at least one processor, and theinstructions are executed by the at least one processor so that the atleast one processor is able to execute the previously described dataprocessing method.

The embodiments of the present specification provide a computer readablestorage medium, storing computer executable instructions that, whenexecuted by a processor, implement the previously described dataprocessing method.

The previously described at least one technical solution adopted in theembodiments of the present specification can achieve the followingbeneficial effects:

The use of data can be systematically managed and controlled because thedata needs to be approved by each approver before being used, so thatthe effectiveness and efficiency of data management and control areimproved, and the use security of the data is improved.

BRIEF DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the presentspecification or the technical solutions in the existing technology, theaccompanying drawings used in the description of the embodiments of thepresent specification or the existing technology will be brieflydescribed below. Clearly, the drawings in the following description areonly some of the embodiments described in the present specification, andfor a person of ordinary skill in the art, other drawings can beobtained based on these drawings without involving any creative effort.

FIG. 1 is a schematic diagram illustrating an executive subject of adata processing method, according to a first embodiment of the presentspecification;

FIG. 2 is a schematic flowchart illustrating a data processing method,according to a first embodiment of the present specification;

FIG. 3 is a schematic diagram illustrating a data processing process,according to a first embodiment of the present specification; and

FIG. 4 is a schematic structural diagram illustrating a data processingapparatus, according to a fourth embodiment of the presentspecification.

DESCRIPTION OF EMBODIMENTS

In order for a person skilled in the art to better understand thetechnical solutions in the present specification, the technicalsolutions in the embodiments of the present application will be clearlyand comprehensively described below with reference to the accompanyingdrawings in the embodiments of the present application. Clearly, thedescribed embodiments are only a part of the embodiments of the presentapplication and not all embodiments. All other embodiments obtained by aperson of ordinary skill in the art based on the embodiments of thepresent specification without involving creative effort should fallwithin the scope of protection of the present application.

At present, the Internet generates and stores various data, includingdata related to user privacy and other privacy, and how to controllablyuse the Internet data is an important issue.

A first embodiment of the present specification provides a dataprocessing method, and an executive subject of the present embodimentcan be an end-user device (including but not limited to a mobile phone,a computer, a pad, and a television) or a server or a corresponding dataprocessing platform or an operating system, etc. That is, the executivesubject can be various, and the executive subject can be set, used, ortransformed as needed. In addition, a third-party application canalternatively be provided to assist the executive subject in executingthe present embodiment. For example, as shown in FIG. 1, the dataprocessing method in the present embodiment can be executed by a server,and an application (corresponding to the server) can be installed on anend-user device (held by a user), the end-user device and the server, orthe application and the server can perform data transmission, and datacollection or input or output, or page presentation, or informationpresentation (to the user) can be performed through the end-user deviceor the application, thereby assisting the server in executing the dataprocessing method in the present embodiment.

In particular, the executive subject of the present embodiment can be anode in a blockchain or a server serving a blockchain.

As shown in FIG. 2 and FIG. 3, the data processing method provided bythe present embodiment includes the following:

S101. (An executive subject) receives a data use request, and determinesdata to be used based on the data use request.

In the present embodiment, the executive subject can receive a data userequest (or data use application). The data use request is aninstruction requesting the use of certain data. The data use request caninclude data information requested to be used, including, but notlimited to, the type, name, capacity, etc. of data requested to be used.A sender of the data use request can be an end-user device, a server,and other subjects. The data use request can further include informationof the sender (or data user) of the data use request to determine thesender from the data use request.

After a data use request is received, “data requested to be used”, i.e.data to be used, corresponding to the data use request can be determinedbased on the data use request. As above, since the data use request caninclude various attributes such as the type, name, and capacity of datarequested to be used, data to be used can be determined based on theseattributes.

In the present embodiment, the data to be used can be data stored by theexecutive subject. The data to be used can be registered data on theexecutive subject or other subjects. In the present embodiment, data tobe registered can be obtained firstly, and then the data to beregistered can be registered, so that the data to be registered becomesregistered data. Specifically, data registration can be performed on theexecutive subject or other subjects by one or more of 1.1 to 1.8 (thepresent embodiment is not limited to the content described in 1.1 to1.8):

1.1. An executive subject generates data to be registered.

In the present embodiment, the executive subject can generate variousdata at any time. For example, the executive subject is a service serverfor providing certain services to users, and the executive subject cangenerate corresponding data when users use the services. For example,the executive subject is a social service server, and the executivesubject generates corresponding data when users use social services. Theexecutive subject is a financial service server, and the executivesubject generates corresponding data when users use financial services.The data generated by the executive subject can be used as data to beregistered, or data satisfying a predetermined condition in the datagenerated by the executive subject can be used as data to be registered,where the predetermined condition can be set based on actual needs.

The executive subject can generate identification data corresponding tothe data to be registered, where the identification data is used forrepresenting the data to be registered corresponding to theidentification data. The executive subject can respectively generatecorresponding identification data for different data to be registered.

For any data A to be registered, the executive subject can register dataA to be registered based on identification data corresponding to data Ato be registered, so that data A to be registered becomes registereddata, that is, data A to be registered is used as registered data.Specifically, registering data A to be registered can include storingdata A to be registered and a mapping relationship between data A to beregistered and identification data corresponding to data A to beregistered, similarly hereinafter.

1.2. An executive subject receives data to be registered.

In the present embodiment, data to be registered can be issued to theexecutive subject by other subjects (e.g., data owner), but notgenerated by the executive subject, and then the executive subjectgenerates corresponding identification data for the data to beregistered. The process of generating identification data andregistering is the same as 1.1.

1.3. An executive subject receives data to be registered andidentification data.

In the present embodiment, the executive subject can receive data to beregistered and identification data corresponding to the data to beregistered, thereby registering the data to be registered based on theidentification data corresponding to the data to be registered, andtaking the data to be registered as registered data. The registrationprocess is the same as 1.1.

1.4. An executive subject executes at least one of receiving and/orgenerating data to be registered and identification data respectively.

In the present embodiment, the executive subject can execute at leastone of generating or receiving data to be registered, and then send aregistration request corresponding to the data to be registered to aspecified blockchain node so that the specified blockchain nodegenerates identification data corresponding to the data to beregistered.

The executive subject can receive the identification data correspondingto the data to be registered sent by the specified blockchain node,register the data to be registered based on the identification datacorresponding to the data to be registered, and take the data to beregistered as registered data.

For example, for any data B to be registered generated or received bythe executive subject, the executive subject sends a registrationrequest corresponding to data B to be registered to a specifiedblockchain node so that the specified blockchain node generatesidentification data corresponding to data B to be registered and returnsthe data to the executive subject. The executive subject receives theidentification data corresponding to data B to be registered sent by thespecified blockchain node, and registers data B to be registered basedon the identification data corresponding to data B to be registered.

1.5. An executive subject executes at least one of generating orreceiving data to be registered and makes it reach a consensus.

In the present embodiment, the executive subject can execute at leastone of generating or receiving data to be registered and generateidentification data for the data to be registered; or receiving data tobe registered and identification data corresponding to the data to beregistered.

The executive subject can send the data to be registered and theidentification data corresponding to the data to be registered to aspecified blockchain node, so that the specified blockchain nodeperforms a consensus on the data to be registered and the identificationdata corresponding to the data to be registered, and the specifiedblockchain node registers the data to be registered based on theidentification data corresponding to the data to be registered after theconsensus (for the data to be registered and the identification datacorresponding to the data to be registered) is reached, and take thedata to be registered as registered data.

For example, for any data C to be registered generated or received bythe executive subject, the executive subject generates correspondingidentification data for data C to be registered; or the executivesubject receives data C to be registered and identification datacorresponding to data C to be registered; the executive subject sendsdata C to be registered and identification data corresponding to data Cto be registered to a specified blockchain node, so that the specifiedblockchain node performs a consensus on data C to be registered and theidentification data corresponding to data C to be registered; and afterthe consensus for data C to be registered and the identification datacorresponding to data C to be registered is reached, the specifiedblockchain node registers data C to be registered based on theidentification data corresponding to data C to be registered. Theregistration process is the same as 1.1.

1.6. An executive subject executes at least one of generating orreceiving data to be registered and performs a consensus.

In the present embodiment, the executive subject can execute at leastone of generating or receiving data to be registered and generateidentification data for the data to be registered; or, receiving data tobe registered and identification data corresponding to the data to beregistered.

If the executive subject is a consensus node of a blockchain, theexecutive subject can perform a consensus on the data to be registeredgenerated by the executive subject and the identification datacorresponding to the data to be registered (besides the executivesubject, other consensus nodes in the same blockchain can alternativelyperform a consensus on the data to be registered and the identificationdata corresponding to the data to be registered), register the data tobe registered based on the identification data corresponding to the datato be registered after the consensus is reached, and take the data to beregistered as registered data. The registration process is the same as1.1.

For example, for any data D to be registered generated or received bythe executive subject, the executive subject generates correspondingidentification data for data D to be registered; or the executivesubject receives data D to be registered and identification datacorresponding to data D to be registered; the executive subject performsa consensus on data D to be registered and the identification datacorresponding to data D to be registered; and after the consensus fordata D to be registered and the identification data corresponding todata D to be registered is reached, data D to be registered isregistered based on the identification data corresponding to data D tobe registered.

1.7. An executive subject receives data to be registered that hasreached consensus and identification data corresponding to the data tobe registered.

In the present embodiment, the executive subject can receive data to beregistered and identification data corresponding to the data to beregistered that has reached consensus by consensus nodes of otherblockchains, register the data to be registered based on theidentification data corresponding to the data to be registered, and takethe data to be registered as registered data. The registration processis the same as 1.1.

1.8. An executive subject executes at least one of generating orreceiving data to be registered and performs a common consensus.

In the present embodiment, the executive subject can execute at leastone of generating or receiving data to be registered, and generateidentification data for the data to be registered; or, receiving data tobe registered and identification data corresponding to the data to beregistered.

The executive subject performs a consensus on the data to be registeredand the identification data corresponding to the data to be registered,registers the data to be registered based on the identification datacorresponding to the data to be registered after the consensus isreached, and takes the data to be registered as registered data; and theexecutive subject sends the data to be registered and the identificationdata corresponding to the data to be registered to a specifiedblockchain node so that the specified blockchain node performs aconsensus on the data to be registered and the identification datacorresponding to the data to be registered, and the specified blockchainnode registers the data to be registered based on the identificationdata corresponding to the data to be registered after the consensus isreached, and takes the data to be registered as registered data.

For example, for any data E to be registered generated or received bythe executive subject, the executive subject generates correspondingidentification data for data E to be registered; or the executivesubject receives data E to be registered and identification datacorresponding to data E to be registered; the executive subject canperform a consensus (which may be referred to as a first consensus) ondata E to be registered and the identification data corresponding todata E to be registered, and registers data E to be registered based onthe identification data corresponding to data E to be registered afterthe first consensus is reached; and the executive subject sends data Eto be registered and the identification data corresponding to data E tobe registered to a specified blockchain node, so that the specifiedblockchain node performs a consensus (which may be referred to as asecond consensus) on data E to be registered and the identification datacorresponding to data E to be registered, and the specified blockchainnode registers data E to be registered based on the identification datacorresponding to data E to be registered after the second consensus isreached.

It can be seen from the above that “obtaining data to be registered” inthe present embodiment can be that the executive subject executes atleast one of generating data to be registered or receiving data to beregistered.

In addition to the content described in 1.1 to 1.8, there can be otherways to register data.

It can be seen from the previous content that the executive subject canregister data to be registered, and other subjects (e.g., specifiedblockchain node) can register data to be registered. Regardless of beingregistered by any subject, data to be registered becomes registereddata. After data to be used is determined, it can then be determinedwhether the data to be used is registered and whether it is registered(or stored) on the executive subject or on other subjects.

Through any of the previously described consensus processes, a consensuscan be performed on data to be registered and identification datacorresponding to the data to be registered, and the data is registeredafter the consensus is reached, so that the data to be registered andthe identification data corresponding to the data to be registered areprevented from being tampered by utilizing the non-tamperingcharacteristic of a blockchain, and the security and credibility of thedata are ensured.

When data registration is performed, the data to be registered can beregistered based on a predetermined template. In addition, a customtemplate can alternatively be adopted, modified content can be added anddeleted from the custom template as needed, and the custom template isused for data registration. For example, the content of thepredetermined template or the custom template includes, but is notlimited to, approver information and approval authority informationcorresponding to each approver, or the content of the predeterminedtemplate or the custom template includes, but is not limited to,approval rules corresponding to data registration, and the approvalrules can include approver information and approval authorityinformation corresponding to each approver. Setting an approval rule fordata is equivalent to setting an approval process after the data isapplied for use, that is, setting an approver and an approval authority.

In the present embodiment, the approver can be at least one of an ownerof the data to be used or a storage party of the data to be used. “Ownerof data to be used” and “storage party of data to be used” describedhere can be the same or different. For example, if the data to be usedis service data of a certain service, the owner and the storage party ofthe data to be used can be service providers of the service (the serviceproviders can be servers or other products). For another example,company X uses an own server to provide a certain service and maintainthe service, service data of the service is stored on the server ofcompany X, and company X (or the server of company X) is the owner andthe storage party of the service data of the service. For anotherexample, company X rents a server of company Y to provide a certainservice and maintain the service, the owner of the service data of theservice can be company X since company X is a nominal provider of theservice, and the storage party of the service data of the service is theserver of company Y.

In addition, the owner of the data to be used can alternatively be auser (or a user account). For example, the owner of some data relatingto user privacy can be a user.

In addition, the approver can further include a primary approver or asecondary approver, and each approver has a corresponding approvalauthority. The primary approver can have a primary approval authority,and the secondary approver can have a secondary approval authority. Forexample, the primary approval authority can be a priority approvalauthority, and the secondary approval authority can be a signed approval(on the basis of a primary approval).

For example, for any data C to be registered, the content of thepredetermined or custom template includes, but is not limited to,approvers corresponding to the registration of data C and an approvalauthority of each approver, as shown in Table 1 (Table 1 is forillustration only):

TABLE 1 Data name Approver Approval character Approval authority Data CApprover 1 Primary approver Primary approval Approver 2 Secondary Signedapproval approver

In the present embodiment, some subjects can be registered on theexecutive subject or other subjects. Specifically, subject registrationcan be performed on the executive subject or other subjects by one ormore of 2.1 to 2.7 (the present embodiment is not limited to the contentdescribed in 2.1 to 2.7):

2.1. An executive subject receives a registration request.

In the present embodiment, the executive subject can receive aregistration request, the registration request can be sent by aregistration requester or other subjects (for example, the registrationrequest sends a registration request to the other subjects, the othersubjects send the registration request to the executive subject,similarly hereinafter), and the executive subject can determine aregistration requester corresponding to the registration request. Theregistration requester can be a server or an end-user device, etc., andthe registration request can contain attribute data of the registrationrequester, including but not limited to the name, type, etc. of theregistration requester.

The executive subject can generate identity data corresponding to theregistration requester, where the identity data is used for representingthe registration requester corresponding to the identity data. Theexecutive subject can respectively generate corresponding identity datafor different registration requesters.

For any registration requester a, the executive subject can registerregistration requester a based on identity data corresponding toregistration requester a, and take registration requester a as aregistered party after the registration is successful. Specifically,registering registration requester a can include storing registrationrequester a and a mapping relationship between registration requester aand identification data corresponding to registration requester a,similarly hereinafter.

2.2. An executive subject receives identity data.

In the present embodiment, the executive subject can receive identitydata corresponding to a registration requester, and determine acorresponding registration requester based on the identity data. Theexecutive subject registers the corresponding registration requesterbased on the identity data, and takes the registration requester as aregistered party, referring to 2.1.

2.3. An executive subject respectively receives a registration requestand identity data.

In the present embodiment, the executive subject can receive aregistration request, can determine a registration requestercorresponding to the registration request, can send the registrationrequest to a specified blockchain node so that the specified blockchainnode determines the registration requester corresponding to theregistration request, and can generate identity data corresponding tothe registration requester.

The executive subject can receive the identity data corresponding to theregistration requester sent by the specified blockchain node, registerthe registration requester based on the identity data corresponding tothe registration requester, and take the registration requester as aregistered party.

For example, the executive subject receives a registration request,determines registration requester b corresponding to the registrationrequest, sends the corresponding registration request to a specifiedblockchain node so that the specified blockchain node determinesregistration requester b corresponding to the registration request, andgenerates identity data corresponding to registration requester b. Theexecutive subject can receive the identity data corresponding toregistration requester b sent by the specified blockchain node, andregister registration requester b based on the identity datacorresponding to registration requester b, so that registrationrequester b becomes a registered party.

2.4. An executive subject receives at least one of a registrationrequest or identity data and makes them reach a consensus.

In the present embodiment, the executive subject can execute at leastone of receiving a registration request, determining a registrationrequester corresponding to the registration request, and generatingcorresponding identity data for the registration requester; or,receiving identity data corresponding to a registration requester, anddetermining a corresponding registration requester based on the identitydata.

The executive subject can send the identity data to a specifiedblockchain node, so that the specified blockchain node performs aconsensus on the identity data and the specified blockchain noderegisters the registration requester based on the identity datacorresponding to the registration requester after the consensus isreached, and take the registration requester as a registered party.

For example, the executive subject receives a registration request,determines registration requester c corresponding to the registrationrequest, and generates corresponding identity data for registrationrequester c; or, the executive subject receives identity datacorresponding to registration requester c; the executive subject sendsthe identity data to a specified blockchain node, so that the specifiedblockchain node determines registration requester c based on theidentity data, and performs a consensus on the identity data; and thespecified blockchain node registers registration requester c based onthe identity data corresponding to registration requester c after theconsensus for the identity data is reached, so that registrationrequester c becomes a registered party.

2.5. An executive subject receives at least one of a registrationrequest or identity data and performs a consensus.

In the present embodiment, the executive subject can execute at leastone of receiving a registration request, determining a registrationrequester corresponding to the registration request, and generatingcorresponding identity data for the registration requester; or,receiving identity data corresponding to a registration requester, anddetermining a corresponding registration requester based on the identitydata.

If the executive subject is a consensus node of a blockchain, theexecutive subject can perform a consensus on the identity data (besidesthe executive subject, other consensus nodes in the same blockchain canalternatively perform a consensus on the identity data), register theregistration requester based on the identity data corresponding to theregistration requester after the consensus is reached, and take theregistration requester as a registered party.

For example, the executive subject receives a registration request,determines registration requester d corresponding to the registrationrequest, and generates corresponding identity data for registrationrequester d; or, the executive subject receives identity datacorresponding to registration requester d; the executive subjectperforms a consensus on the identity data corresponding to registrationrequester d; and registration requester d is registered based on theidentity data corresponding to registration requester d after theconsensus for the identity data is reached, so that registrationrequester d becomes a registered party.

2.6. An executive subject receives identity data that has reachedconsensus.

In the present embodiment, the executive subject can receive identitydata corresponding to a registration requester that has reachedconsensus by consensus nodes of other blockchains, determine acorresponding registration requester based on the identity data,register the registration requester corresponding to the identity databased on the identity data, and take the registration requester as aregistered party.

2.7. An executive subject receives at least one of a registrationrequest or identity data and performs a common consensus.

In the present embodiment, the executive subject can execute at leastone of receiving a registration request, determining a registrationrequester corresponding to the registration request, and generatingcorresponding identity data for the registration requester; or,receiving identity data corresponding to a registration requester, anddetermining a corresponding registration requester based on the identitydata.

The executive subject can perform a consensus on the identity data,register the registration requester based on the identity datacorresponding to the registration requester after the consensus isreached, and take the registration requester as a registered party; andthe executive subject can send the identity data to a specifiedblockchain node so that the specified blockchain node performs aconsensus on the identity data and the specified blockchain noderegisters the registration requester based on the identity datacorresponding to the registration requester after the consensus isreached, and take the registration requester as a registered party.

For example, the executive subject receives a registration request,determine registration requester e corresponding to the registrationrequest, and generate corresponding identity data for registrationrequester e; or the executive subject receives identity datacorresponding to registration requester e; the executive subject canperform a consensus (which may be referred to as a third consensus) onthe identity data, and register registration requester e based on theidentity data corresponding to registration requester e after the thirdconsensus is reached so that registration requester e becomes aregistered party; the executive subject sends the identity data to aspecified blockchain node so that the specified blockchain nodedetermines registration requester e based on the identity data, andperforms a consensus (which may be referred to as a fourth consensus) onthe identity data; and the specified blockchain node registersregistration requester e based on the identity data corresponding toregistration requester e after the fourth consensus is reached, so thatregistration requester e becomes a registered party.

In addition to the content described in 2.1 to 2.7, there can be otherways to register a registration requester.

It can be seen from the previous content that the executive subject canregister a registration requester, and other subjects (e.g., specifiedblockchain node) can register a registration requester. Regardless ofbeing registered by any subject, a registration requester becomes aregistered party. After a data use request is received, it can then bedetermined whether a sender of the data use request is registered andwhether it is registered (or stored) on the executive subject or onother subjects.

Through any of the previously described consensus processes, a consensuscan be performed on the identity data, and a registration requester isregistered after the consensus is reached, so that the identity data isprevented from being tampered by utilizing the non-tamperingcharacteristic of a blockchain, and the security and credibility of thedata are ensured.

When a registration requester is registered, the registration requestercan be registered based on a predetermined template or a customtemplate.

The registration requester includes at least one of an owner of the datato be used, a storage party of the data to be used, or the approver.

In the present embodiment, each time a data use request is received, aprocessor identifier can be generated for the data use request; and/or,each time a data use request is received, a process registrationinstruction can be sent to a specified blockchain node so that thespecified blockchain node generates a process identifier for the datause request; and the specified blockchain node sends the processidentifier to the executive subject, and the executive subject receivesthe process identifier.

Through the consensus for a process identifier, the generated processidentifier can be prevented from being tampered by utilizing thenon-tampering characteristic of a blockchain, and the security andcredibility of the process identifier are ensured.

As described above, the executive subject of the present embodiment canbe a node in a blockchain or a server serving the blockchain, thespecified blockchain node and the executive subject can belong to thesame blockchain, and the specified blockchain node can be all or part ofnodes in the blockchain, for example, can be all or part of consensusnodes in the blockchain. In the present embodiment, existing consensusalgorithms can be used for consensus.

S103. (The executive subject) determines one or more approverscorresponding to the data to be used.

After data to be used is determined, one or more approvers correspondingto the data to be used can be determined; or, an approval rulecorresponding to the data to be used can be determined, where theapproval rule can include one or more approvers (needs to approve thedata use request), i.e., approvers corresponding to the data to be used.For example, when any data is registered, an approver corresponding tothe data has been set, and if the data belongs to the data to be used,the approver corresponding to the data belongs to the approvercorresponding to the data to be used.

In particular, the approver can include a user corresponding to the datato be used. For example, the data to be used includes transaction data,where the transaction data is generated by user F using a financialtransaction, and then user F is a user corresponding to the data to beused.

In the present embodiment, in addition to determining the approvercorresponding to the data to be used, an approval authority or anapproval process of each approver corresponding to the data to be usedcan further be determined; or, in addition to the approvers, theapproval rule can include an approval authority of each approver or anapproval process of each approver, etc. The approval authority of eachapprover can be determined when data registration is performed, forexample, as shown in Table 1, the approver and the approval authoritycorresponding to the registered data are set; or after each approvercorresponding to the data to be used is determined, the approvalauthority of each approver is determined. For example, the approvalauthority of the approver is determined based on the authority of eachapprover corresponding to the data to be used, and a relationship withthe data to be used.

The approval process can include an approval priority or an approvalorder of each approver, for example, if the approver corresponding tothe data to be used includes a primary approver and a secondaryapprover, the approval can be performed by the primary approver first,and then the approval can be performed by the secondary approver on thebasis of the approval of the primary approver. In addition, the approvalresults of each approver can be forwarded to each other.

In particular, the executive subject of the present embodiment canalternatively be one of the approvers corresponding to the data to beused.

S105. The (executive subject) sends an approval instruction to eachapprover, where the approval instruction is used for instructing eachapprover to approve the data use request.

After one or more approvers (corresponding to the data to be used) aredetermined, the executive subject can send an approval instruction toeach determined approver, where the approval instruction is used forinstructing each approver to approve the data use request (for example,the approval instruction can include a statement such as “Please approvea data use request of XX data”). Therefore, each approver approves thedata use request based on the respective approval authorities.

In the present embodiment, because each data use request corresponds toa process identifier, which is equivalent to that each data use requestcorresponds to a data use approval process, the previously describedapproval instruction can further enable each approver to approve theprocess identifier, so that each approver can accurately distinguishdifferent data use approval processes.

It is worthwhile to note that an actual approver may be a corporategroup or a natural person, etc., but a recipient of an approvalinstruction can be an electronic device or a network account mastered orowned by the approver, such as a computer, a mobile phone, a server, ora network account logged on the server. In the present embodiment,sending an approval instruction to an electronic device or a networkaccount mastered or owned by an approver is considered to be sending anapproval instruction to the approver.

After the electronic device or the network account mastered or owned bythe approver receives the approval instruction, approval information orpages corresponding to the approval instruction can be presented forapproval of the approver.

If the executive subject is one of the approvers, the executive subjectcan generate and present approval information or pages corresponding tothe approval instruction (the executive subject is considered to sendthe approval instruction to the executive subject), so that the owner ofthe executive subject performs approval.

S107. (The executive subject) receives approval feedback data of eachapprover, and determines that the data use request is approved if theapproval feedback data satisfies a predetermined condition.

In the present embodiment, after an approver approves an approvalinstruction using an electronic device or a network account mastered orowned by the approver, the approver can send approval feedback data(i.e. an approval result) to the executive subject via the electronicdevice or the network account. Receiving approval feedback data sent byan electronic device or a network account mastered or owned by anapprover is regarded as receiving approval feedback data of theapprover.

The executive subject receives approval feedback data of each approver,and determines that the data use request is approved if the approvalfeedback data satisfies a predetermined condition.

In the present embodiment, it is possible to determine whether theapproval feedback data satisfies a predetermined condition and whetherthe data use request is approved based on one or more of 3.1 to 3.7 (thepresent embodiment is not limited to the content described in 3.1 to3.7)

3.1. The executive subject can determine whether the approval feedbackdata of each approver indicates the approval or not, similarlyhereinafter. If the executive subject determines that all approvers givethe approval based on the approval feedback data, the approval feedbackdata satisfies the predetermined condition, and it can be determinedthat the data use request is approved.

3.2. If the executive subject determines that at least one approver doesnot give the approval based on the approval feedback data, the approvalfeedback data does not satisfy the predetermined condition, and it canbe determined that the data use request is not approved.

3.3. If the executive subject determines that the number of approversreaches a predetermined threshold based on the approval feedback data,the approval feedback data satisfies the predetermined condition, and itcan be determined that the data use request is approved.

3.4. If the executive subject determines that the number of approversdoes not reach a predetermined threshold based on the approval feedbackdata, the approval feedback data does not satisfy the predeterminedcondition, and it can be determined that the data use request is notapproved.

3.5. If one or more approvers corresponding to the data to be usedinclude a primary approver and the executive subject determines that aratio of the number of primary approvers that provide approval to thenumber of approvers corresponding to the data to be used satisfies apredetermined ratio condition based on the approval feedback data (forexample, the predetermined ratio condition is that the ratio is greaterthan a half), the approval feedback data satisfies the predeterminedcondition, and it can be determined that the data use request isapproved.

3.6. If one or more approvers corresponding to the data to be usedinclude a primary approver and the executive subject determines that aratio of the number of primary approvers that provide approval to thenumber of approvers corresponding to the data to be used does notsatisfy a predetermined ratio condition based on the approval feedbackdata (for example, the predetermined ratio condition is that the ratiois greater than a half), the approval feedback data does not satisfy thepredetermined condition, and it can be determined that the data userequest is not approved.

3.7. If one or more approvers corresponding to the data to be usedinclude a primary approver and the executive subject determines that atleast one approver does not give approval, the data use request is notapproved.

It can be seen that the predetermined condition can be a numbercondition or a ratio condition, so that it can be determined whether theapproval feedback data satisfies the predetermined condition based onthe number or ratio of approvers which give the approval or not.

If it is determined that the data use request is approved, the data tobe used can be sent to a sender of the data use request. If the data tobe used is stored or registered on the executive subject, the executivesubject sends the data to be used to the sender of the data use request.If the data to be used is not stored or registered on the executivesubject, the executive subject can send an instruction to a subjectstoring the data to be used or a subject registering the data to beused, so that the subject storing the data to be used or the subjectregistering the data to be used sends the data to be used to the senderof the data use request. Or, if the data to be used is not stored orregistered on the executive subject, the executive subject can send aninstruction to a subject storing the data to be used or a subjectregistering the data to be used, so that the subject storing the data tobe used or the subject registering the data to be used sends the data tobe used to the executive subject, and the executive subject sends thedata to be used to the sender of the data use request.

In addition, approval records of the data use request and data userecords (which can be in the form of logs) can be queried and audited tofacilitate systematic management of data use.

In the present embodiment, after the data to be used is determined, theexecutive subject can determine whether the data to be used isregistered data. If yes, processes S103 to S107 are executed. If no,S103 is not executed, thus, \ S105 and subsequent processes are omitted.And/or, in the present embodiment, after the data use request isreceived, the executive subject can determine whether the sender of thedata use request is a registered party. If yes, data to be used isdetermined, and processes S103 to S107 are executed. If no, the data tobe used is not determined, and S103 and subsequent processes areomitted.

In the present embodiment, the use of data can be systematically managedand controlled because the data needs to be approved by each approverbefore being used, so that the effectiveness and efficiency of datamanagement and control are improved, and the use security of the data isimproved. Since the data is registered through the identification data,registered data can be accurately positioned and distinguished, and ifthe data to be used is the registered data, the data to be used can beaccurately positioned. If the registration requester is registeredthrough the identity data, a registrant can be accurately positioned anddistinguished, and if the sender of the data use request is theregistrant, the registrant can be accurately positioned. On this basis,only the registrant can be allowed to send the data use request, so thata user who requests the data can be screened, and the management of datause is facilitated. Each data use request and corresponding approval andother processes can be accurately distinguished through the processidentifier, mutual interference between the data use requests isalleviated, and the processing efficiency of data use is improved.

In the present embodiment, data registration, registration requesterregistration, process registration, etc. can be established (orregistered) on a blockchain, and the blockchain performs a consensus.The approver can further include a blockchain node, and the blockchainperforms a consensus on data (including approval feedback data) in thewhole approval process, i.e. the present embodiment can be implementedby a node in the blockchain or a blockchain service provider, and theblockchain provides a trusted environment and performs a consensus forthe present embodiment (including various registration processes, datain the registration processes, such as identification data, identitydata, and process identifiers), approval processes, and data in theapproval processes (such as approval feedback data) in the presentembodiment). Therefore, the blockchain provides services such as processmanagement service and data authorization use in the present embodiment,various data involved in the present embodiment can be prevented frombeing tampered, and the security and credibility of the presentembodiment can be improved.

In the present embodiment, since the data to be used may be generated bya user as a result of performing an on-line operation (e.g., using anon-line service), the data to be used may include data more closelyrelated to the user, such as privacy data including user identityinformation. In the present embodiment, the user can be used as anapprover of certain data, so that the user can alternatively approvecertain data to be used (e.g., an instruction or a message aboutapproval can be sent to an account of the user or an account loginend-user device so as to facilitate approval of the user), the rights toknow and ownership of personal data by the user are guaranteed, and thedata security of the user is favorably maintained.

As shown in FIG. 4, a second embodiment of the present specificationprovides a data processing apparatus, including the following:

a data determination module 201, configured to receive a data userequest, and determine data to be used based on the data use request;

an approval determination module 203, configured to determine one ormore approvers corresponding to the data to be used;

an approval initiation module 205, configured to send an approvalinstruction to each approver, where the approval instruction is used forinstructing each approver to approve the data use request; and

an approval judgment module 207, configured to receive approval feedbackdata of each approver, and determine that the data use request isapproved if the approval feedback data satisfies a predeterminedcondition.

Optionally, the apparatus further includes the following:

a registration module, configured to: obtain data to be registered, andgenerate corresponding identification data for the data to beregistered; and

register the data to be registered based on the identification data, andtake the data to be registered as registered data;

or,

receive data to be registered and identification data corresponding tothe data to be registered; and

register the data to be registered based on the identification data, andtake the data to be registered as registered data.

Optionally, the apparatus further includes the following:

a registration module, configured to: obtain data to be registered, andsend a registration request corresponding to the data to be registeredto a specified blockchain node, so that the specified blockchain nodegenerates identification data corresponding to the data to beregistered; and

receive the identification data corresponding to the data to beregistered sent by the specified blockchain node, register the data tobe registered based on the identification data, and take the data to beregistered as registered data;

or,

perform at least one of obtaining data to be registered and generatingcorresponding identification data for the data to be registered, and/or,receiving data to be registered and identification data corresponding tothe data to be registered;

send the data to be registered and the identification data correspondingto the data to be registered to a specified blockchain node, so that thespecified blockchain node performs a consensus on the data to beregistered and the identification data corresponding to the data to beregistered, and the specified blockchain node registers the data to beregistered based on the identification data corresponding to the data tobe registered after the consensus is reached, and take the data to beregistered as registered data;

or,

execute at least one of obtaining data to be registered and generatingcorresponding identification data for the data to be registered, or,receiving data to be registered and identification data corresponding tothe data to be registered;

perform a consensus on the data to be registered and the identificationdata corresponding to the data to be registered, register the data to beregistered based on the identification data corresponding to the data tobe registered after the consensus is reached, and take the data to beregistered as registered data;

or,

receive data to be registered that has reached consensus andidentification data corresponding to the data to be registered, registerthe data to be registered based on the identification data correspondingto the data to be registered, and take the data to be registered asregistered data.

Optionally, the apparatus further includes the following:

a registration module, configured to: execute at least one of obtainingdata to be registered and generating corresponding identification datafor the data to be registered, and/or, receiving data to be registeredand identification data corresponding to the data to be registered;

perform a consensus on the data to be registered and the identificationdata corresponding to the data to be registered, register the data to beregistered based on the identification data corresponding to the data tobe registered after the consensus is reached, and take the data to beregistered as registered data; and send the data to be registered andthe identification data corresponding to the data to be registered to aspecified blockchain node so that the specified blockchain node performsa consensus on the data to be registered and the identification datacorresponding to the data to be registered, and the specified blockchainnode registers the data to be registered based on the identificationdata corresponding to the data to be registered after the consensus isreached, and take the data to be registered as registered data.

Optionally, the apparatus further includes the following:

a registration module, configured to register the data to be registeredbased on a predetermined template or a custom template.

Optionally, the predetermined template or the custom template includesapprover information.

Optionally, the predetermined template or the custom template includesapproval authority information.

Optionally, the apparatus further includes the following:

a registration module, configured to: receive a registration request,determine a registration requester corresponding to the registrationrequest, and generate corresponding identity data for the registrationrequester; and

register the registration requester based on the identity data, and takethe registration requester as a registered party;

or,

receive identity data corresponding to a registration requester; and

register the registration requester based on the identity data, and takethe registration requester as a registered party.

Optionally, the apparatus further includes the following:

a registration module, configured to: receive a registration request,determine a registration requester corresponding to the registrationrequest, send the registration request to a specified blockchain node sothat the specified blockchain node determines the registration requestercorresponding to the registration request, and generate identity datacorresponding to the registration requester; and

receive the identity data sent by the specified blockchain node,register the registration requester based on the identity data, and takethe registration requester as a registered party;

or,

receive a registration request, determine a registration requestercorresponding to the registration request, and generate correspondingidentity data for the registration requester, or receive identity datacorresponding to a registration requester;

send the identity data to a specified blockchain node so that thespecified blockchain node performs a consensus on the identity data, andthe specified blockchain node registers the registration requester basedon the identity data corresponding to the registration requester afterthe consensus is reached, and take the registration requester as aregistered party;

or,

receive a registration request, determine a registration requestercorresponding to the registration request, and generate correspondingidentity data for the registration requester, or receive identity datacorresponding to a registration requester;

perform a consensus on the identity data, register the registrationrequester based on the identity data corresponding to the registrationrequester after the consensus is reached, and take the registrationrequester as a registered party;

or,

receive identity data corresponding to a registration requester that hasreached consensus, register the registration requester corresponding tothe identity data based on the identity data, and take the registrationrequester as a registered party.

Optionally, the apparatus further includes the following:

a registration module, configured to: receive a registration request,determine a registration requester corresponding to the registrationrequest, and generate corresponding identity data for the registrationrequester, or receive identity data corresponding to a registrationrequester;

perform a consensus on the identity data, register the registrationrequester based on the identity data corresponding to the registrationrequester after the consensus is reached, and take the registrationrequester as a registered party; and send the identity data to aspecified blockchain node so that the specified blockchain node performsa consensus on the identity data, and the specified blockchain noderegisters the registration requester based on the identity datacorresponding to the registration requester after the consensus isreached, and take the registration requester as a registered party.

Optionally, the apparatus further includes the following:

a registration module, configured to register the registration requesterbased on a predetermined template or a custom template.

Optionally, the registration requester includes at least one of an ownerof the data to be used, a storage party of the data to be used, or theapprover.

Optionally, the apparatus further includes the following:

a registration module, configured to: generate a process identifier forthe data use request;

or,

send a process registration instruction to a specified blockchain nodeso that the specified blockchain node generates a process identifier forthe data use request, and receive the process identifier returned by thespecified blockchain node.

Optionally, the approval instruction further enables each approver toapprove the process identifier.

Optionally, the apparatus further includes the following:

a registration module, configured to: determine whether a sender of thedata use request is a registered party; and

if yes, determine data to be used based on the data use request;

or,

after the determining data to be used, the method further includes thefollowing:

it is determined whether the data to be used is registered data, and ifyes, one or more approvers corresponding to the data to be used aredetermined.

Optionally, the approver includes a primary approver or a secondaryapprover, each approver has a corresponding approval authority.

Optionally, the operation of determining that the data use request isapproved if the approval feedback data satisfies a predeterminedcondition includes the following:

if one or more approvers corresponding to the data to be used include aprimary approver, and a ratio of the number of primary approvers thatprovide approval to the number of approvers corresponding to the data tobe used satisfies a predetermined ratio condition, then the approvalfeedback data satisfies a predetermined condition, and it is determinedthat the data use request is approved.

Optionally, after one or more approvers corresponding to the data to beused are determined, the method further includes the following:

an approval authority of each approver is determined.

Optionally, the approver is at least one of an owner of the data to beused or a storage party of the data to be used.

Optionally, the apparatus further includes the following:

a sending module, configured to: send the data to be used to a sender ofthe data use request if it is determined that the data use request isapproved.

A third embodiment of the present specification provides a dataprocessing device, including the following:

at least one processor;

and

a memory communicably coupled to the at least one processor,

where

the memory stores instructions executable by the at least one processor,and the instructions are executed by the at least one processor so thatthe at least one processor is able to execute the data processing methoddescribed in the first embodiment.

A fourth embodiment of the present specification provides a computerreadable storage medium, storing computer executable instructions that,when executed by a processor, implement the data processing methoddescribed in the first embodiment.

The previously described embodiments can be used in combination, andmodules having the same name can be the same or different betweendifferent embodiments.

The specific embodiments of the present specification have beendescribed previously, and other embodiments fall within the scope of theappended claims. In some cases, the actions or steps described in theclaims can be performed in a different order than in one or moreembodiments, and can still achieve desired results. In addition, theprocesses described in the drawings do not necessarily require aspecific order or sequential order shown in order to achieve the desiredresults. In some implementations, multitasking and parallel processingare also possible or may be advantageous.

The various embodiments in the present specification are describedprogressively. The same or similar parts between the various embodimentscan be referred to each other. The various embodiments place emphasis ondifferences from other embodiments. In particular, the apparatus,device, and non-volatile computer readable storage medium embodimentsare simply described since they substantially correspond to the methodembodiments, and reference can be made in part to the description of themethod embodiments.

The apparatus, the device, and the non-volatile computer readablestorage medium provided by the embodiments of the present specificationcorrespond to the method. Therefore, the apparatus, the device, and thenon-volatile computer storage medium also have similar advantageoustechnical effects to the corresponding method. Since the advantageoustechnical effects of the method have been described in detailpreviously, descriptions for the advantageous technical effects of thecorresponding system, apparatus, device, and non-volatile computerstorage medium are omitted here for simplicity.

In the 1990s, improvements to a technology could clearly distinguishbetween improvements in hardware (e.g., improvements to circuitstructures such as diodes, transistors, and switches) and improvementsin software (improvements to method flows). However, with thedevelopment of technologies, many current improvements in method flowshave been regarded as direct improvements in hardware circuit structure.Designers almost always obtain corresponding hardware circuit structuresby programming the improved method flows into hardware circuits.Therefore, it is incorrect to say that an improvement of a method flowcannot be implemented with hardware entity modules. For example, aprogrammable logic device (PLD), such as a field programmable gate array(FPGA), is an integrated circuit with logic functions determined by auser programming the device. It is programmed by a designer to“integrate” a digital system onto a PLD without requiring a chipmanufacturer to design and manufacture application specific integratedcircuit (ASIC) chips. Moreover, nowadays, instead of manuallymanufacturing integrated circuit chips, such programming is mostlyimplemented by using “logic compiler” software, which is similar to asoftware compiler used at the time of program development and writing,and original code to be compiled must also be written in a specificprogramming language, which is referred to as a hardware descriptionlanguage (HDL). There are many HDLs rather than one HDL, such as anadvanced boolean expression language (ABEL), an Altera hardwaredescription language (AHDL), Confluence, a Cornell universityprogramming language (CUPL), HDCal, a Java hardware description language(JHDL), Lava, Lola, MyHDL, PALASM, and a Ruby hardware descriptionlanguage (RHDL). A very-high-speed integrated circuit hardwaredescription language (VHDL) and Verilog are most commonly used atpresent. It is also clear to a person skilled in the art that a hardwarecircuit implementing the logic method flow can be readily obtained byonly slightly logically programming and programming the method flow intoan integrated circuit by using the previous several hardware descriptionlanguages.

A controller can be implemented in any suitable manner. For example, thecontroller can take the form of, for example, a micro processor orprocessor and a computer readable medium storing computer readableprogram code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, ASICs, programmable logic controllers,and embedded micro controllers. Examples of the controller include, butare not limited to, the following micro controllers: ARC 625D, AtmelAT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memorycontroller can also be implemented as a part of the control logic of thememory. A person skilled in the art also understands that, in additionto implementing the controller in pure computer readable program code,it is entirely possible to logically program the method steps such thatthe controller implements the same function in the form of logic gates,switches, ASICs, programmable logic controllers, embedded microcontrollers, etc. Such a controller can thus be regarded as a hardwarecomponent, and an apparatus that is included in the hardware componentand configured to implement various functions can also be regarded as astructure within the hardware component. Or even, the apparatus forimplementing various functions can be regarded as a software moduleimplementing the method and a structure within the hardware component.

The system, apparatus, module, or unit illustrated in the previousembodiments can be specifically implemented by using a computer chip oran entity, or can be implemented by using a product having a certainfunction. A typical implementation device is a computer. Specifically,the computer can be, for example, a personal computer, a laptopcomputer, a cellular phone, a camera phone, a smart phone, a personaldigital assistant, a media player, a navigation device, an emailreceiving and transmitting device, a game console, a tablet computer, awearable device, or any combination of these devices.

For convenience of description, the previous apparatuses are describedas being functionally divided into various units respectively. Ofcourse, the functions of the various units can be implemented in thesame or at least one of a plurality of pieces of software or hardwarewhen implementing the present specification.

A person skilled in the art should understand that the embodiments ofthe present specification can be provided as methods, systems, orcomputer program products. Therefore, the embodiments of the presentspecification can adopt forms of complete hardware embodiments, completesoftware embodiments or embodiments integrating software and hardware.Moreover, the embodiments of the present specification can adopt theform of a computer program product implemented on one or more computeravailable storage media (including, but not limited to, a disk memory, acompact disc read-only memory (CD-ROM), an optical memory, etc.)containing computer available program code.

The present specification is described with reference to at least one offlowcharts or block diagrams of the method, the device (system), and thecomputer program product according to the embodiments of the presentspecification. It should be understood that at least one of each flow orblock in at least one of flowcharts or block diagrams and combinationsof at least one of flows or blocks in at least one of the flowcharts orblock diagrams can be implemented by computer program instructions.These computer program instructions can be provided to a general-purposecomputer, a special-purpose computer, an embedded processor, or aprocessor of another programmable data processing device to generate amachine, such that instructions executed by the computer or theprocessor of the another programmable data processing device produce anapparatus for implementing functions specified in one or more flows inat least one of the flowcharts or one or more blocks in the blockdiagrams.

These computer program instructions can also be stored in a computerreadable memory capable of guiding a computer or another programmabledata processing device to work in a specific way, such that instructionsstored in the computer readable memory produce a product including aninstruction apparatus that implements functions specified in one or moreflows in at least one of the flowcharts or one or more blocks in theblock diagrams.

These computer program instructions can also be loaded to a computer oranother programmable data processing device, such that a series ofoperating steps are performed on the computer or the anotherprogrammable data processing device to produce a computer-implementedprocess, and therefore instructions executed on the computer or theanother programmable data processing device provide steps forimplementing functions specified in one or more flows in at least one ofthe flowcharts or one or more blocks in the block diagrams.

In a typical configuration, the computer includes one or more centralprocessing units (CPUs), one or more input/output interfaces, one ormore network interfaces, and one or more memories.

The memory may include at least one of a non-persistent memory, a randomaccess memory (RAM), or anon-volatile memory in a computer readablemedium, such as a ROM or a flash RAM. The memory is an example of thecomputer readable medium.

The computer readable medium includes persistent, non-persistent,movable, and unmovable media that can store information by using anymethod or technology. The information can be a computer readableinstruction, a data structure, a program module, or other data. Examplesof the computer storage medium include but are not limited to a phasechange random access memory (PRAM), a static RAM (SRAM), a dynamic RAM(DRAM), a RAM of another type, a ROM, an electrically erasableprogrammable ROM (EEPROM), a flash memory or another memory technology,a CD-ROM, a digital versatile disc (DVD), or another optical storage, acassette, a magnetic disk storage, or another magnetic storage device orany other non-transmission medium. The computer storage medium can beconfigured to store information that can be accessed by a computingdevice. As described in the present specification, the computer readablemedium does not include computer readable transitory media such as amodulated data signal and a carrier.

It is also worthwhile to note that the terms “include”, “contain” or anyother term variations are intended to cover a non-exclusive inclusion,such that a process, method, product, or device including a series ofelements includes not only those elements but also other elements notexplicitly listed, or elements that are inherent to such process,method, product, or device. In the absence of more restrictions,elements described by the phrase “include a/an . . . ” do not excludethe existence of additional identical elements in the process, method,article, or device that includes the elements.

The present specification can be described in the general context ofcomputer executable instructions, such as program modules, executed by acomputer. Generally, the program modules include routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular abstract data types. The present specificationcan also be implemented in distributed computing environments wheretasks are performed by remote processing devices that are connectedthrough a communications network. In the distributed computingenvironments, the program modules can be located in both local andremote computer storage media including storage devices.

The various embodiments in the present specification are describedprogressively. The same or similar parts between the various embodimentscan be referred to each other. The various embodiments place emphasis ondifferences from other embodiments. In particular, the systemembodiments are simply described since they substantially correspond tothe method embodiments, and reference will now be made in part to thedescription of the method embodiments.

The previous descriptions are merely embodiments of the presentspecification, and are not intended to limit the present application.Various changes and variations of the present application can occur to aperson skilled in the art. Any modifications, equivalent substitutions,improvements, etc. that come within the spirit and principles of thepresent application are intended to be included within the scope of theclaims of the present application.

What is claimed is:
 1. A computer-implemented method, comprising:receiving a data use request; determining data to be used based on thedata use request; determining one or more approvers of the data to beused; sending an approval instruction to the one or more approvers,wherein the approval instruction instructs the one or more approvers toapprove the data use request; receiving feedback data from the one ormore approvers; and determining that the data use request is approved ifthe feedback data satisfies a predetermined condition.
 2. Thecomputer-implemented method of claim 1, comprising: receiving data to beregistered; determining identification data corresponding to the data tobe registered; and registering the data to be registered based on theidentification data.
 3. The computer-implemented method of claim 1,comprising: obtaining data to be registered; determining identificationdata corresponding to the data to be registered; and sending the data tobe registered and the identification data to a blockchain node toperform a consensus of the data to be registered and the identificationdata to record the data and the identification data on a blockchain. 4.The computer-implemented method of claim 1, comprising: obtaining datato be registered; generating identification data corresponding to thedata to be registered; performing a consensus on the data to beregistered and the identification data corresponding to the data to beregistered; registering the data as registered data based on theidentification data after the consensus is reached; and sending the datato be registered and the identification data to a blockchain node toperform a consensus of the data to be registered and the identificationdata to record the data and the identification data on a blockchain. 5.The computer-implemented method of claim 4, comprising: registering thedata to be registered based on a predetermined template that comprisesat least one of approver information or approval authority information.6. The computer-implemented method of claim 1, comprising: receiving aregistration request; identifying a requester of the registrationrequest; generating identity data corresponding to the registrationrequester; and registering the requester as a registered party based onthe identity data.
 7. The computer-implemented method of claim 6,wherein the requester comprises at least one of an owner of the data tobe used, a recorder of the data to be used, or an approver of the datato be used.
 8. The computer-implemented method of claim 1, comprising:sending a process registration instruction to a blockchain node toinstruct the blockchain node to generate a process identifiercorresponding to the data use request; and receiving the processidentifier from the blockchain node.
 9. The computer-implemented methodof claim 1, comprising: after receiving the data use request:determining that a sender of the data use request is a registered party;determining the data to be used based on the data use request;determining that the data to be used is registered data; and determiningone or more approvers corresponding to the data to be used.
 10. Thecomputer-implemented method of claim 1, wherein the one or moreapprovers comprise one or more primary approvers and one or moresecondary approvers, and wherein the feedback data satisfies thepredetermined condition if a ratio of a number of the one or moreprimary approvers that provide approvals to a number of approverscorresponding to the data to be used satisfies a predetermined ratiocondition.
 11. A non-transitory, computer-readable medium storing one ormore instructions executable by a computer system to perform operationscomprising: receiving a data use request; determining data to be usedbased on the data use request; determining one or more approvers of thedata to be used; sending an approval instruction to the one or moreapprovers, wherein the approval instruction instructs the one or moreapprovers to approve the data use request; receiving feedback data fromthe one or more approvers; and determining that the data use request isapproved if the feedback data satisfies a predetermined condition. 12.The non-transitory, computer-readable medium of claim 11, the operationscomprising: receiving data to be registered; determining identificationdata corresponding to the data to be registered; and registering thedata to be registered based on the identification data.
 13. Thenon-transitory, computer-readable medium of claim 11, the operationscomprising: obtaining data to be registered; determining identificationdata corresponding to the data to be registered; and sending the data tobe registered and the identification data to a blockchain node toperform a consensus of the data to be registered and the identificationdata to record the data and the identification data on a blockchain. 14.The non-transitory, computer-readable medium of claim 11, the operationscomprising: obtaining data to be registered; generating identificationdata corresponding to the data to be registered; performing a consensuson the data to be registered and the identification data correspondingto the data to be registered; registering the data as registered databased on the identification data after the consensus is reached; andsending the data to be registered and the identification data to ablockchain node to perform a consensus of the data to be registered andthe identification data to record the data and the identification dataon a blockchain.
 15. The non-transitory, computer-readable medium ofclaim 14, the operations comprising: registering the data to beregistered based on a predetermined template that comprises at least oneof approver information or approval authority information.
 16. Thenon-transitory, computer-readable medium of claim 11, the operationscomprising: receiving a registration request; identifying a requester ofthe registration request; generating identity data corresponding to theregistration requester; and registering the requester as a registeredparty based on the identity data.
 17. The non-transitory,computer-readable medium of claim 16, wherein the requester comprises atleast one of an owner of the data to be used, a recorder of the data tobe used, or an approver of the data to be used.
 18. The non-transitory,computer-readable medium of claim 11, the operations comprising: sendinga process registration instruction to a blockchain node to instruct theblockchain node to generate a process identifier corresponding to thedata use request; and receiving the process identifier from theblockchain node.
 19. The non-transitory, computer-readable medium ofclaim 11, the operations comprising: after receiving the data userequest: determining that a sender of the data use request is aregistered party; determining the data to be used based on the data userequest; determining that the data to be used is registered data; anddetermining one or more approvers corresponding to the data to be used.20. A computer-implemented system, comprising: one or more computers;and one or more computer memory devices interoperably coupled with theone or more computers and having tangible, non-transitory,machine-readable media storing one or more instructions that, whenexecuted by the one or more computers, perform one or more operationscomprising: receiving a data use request; determining data to be usedbased on the data use request; determining one or more approvers of thedata to be used; sending an approval instruction to the one or moreapprovers, wherein the approval instruction instructs the one or moreapprovers to approve the data use request; receiving feedback data fromthe one or more approvers; and determining that the data use request isapproved if the feedback data satisfies a predetermined condition.